@sepandhaghighi

Since the previous PR touched a large number of files, I wasn’t entirely sure how to update the changelog without making it overly verbose or noisy. I’d appreciate your guidance on the preferred approach. One option is to explicitly list all affected components/files (from this and the previous PR), but I’m not certain that level of granularity is desirable.

After this PR is merged, I plan to publish a new release, close all bug issues, and then proceed with the remaining items.

@sepandhaghighi

Since the previous PR touched a large number of files, I wasn’t entirely sure how to update the changelog without making it overly verbose or noisy. I’d appreciate your guidance on the preferred approach. One option is to explicitly list all affected components/files (from this and the previous PR), but I’m not certain that level of granularity is desirable.

There is no need to mention all components updates in the CHANGELOG.md. If we only mention the fixed bug, it is enough.